CVE-2026-24134
StudioCMS has an Authorization Bypass Through User-Controlled Key
Description
StudioCMS is a server-side-rendered, Astro native, headless content management system. Versions prior to 0.2.0 contain a Broken Object Level Authorization (BOLA) vulnerability in the Content Management feature that allows users with the "Visitor" role to access draft content created by Editor/Admin/Owner users. Version 0.2.0 patches the issue.
INFO
Published Date :
Jan. 28, 2026, 12:15 a.m.
Last Modified :
March 17, 2026, 3:39 p.m.
Remotely Exploit :
Yes !
Source :
[email protected]
CVSS Scores
| Score | Version | Severity | Vector | Exploitability Score | Impact Score | Source |
|---|---|---|---|---|---|---|
| CVSS 3.1 | MEDIUM | [email protected] |
Solution
- Update StudioCMS to version 0.2.0 or later.
- Verify content access controls are enforced.
Public PoC/Exploit Available at Github
CVE-2026-24134 has a 3 public
PoC/Exploit available at Github.
Go to the Public Exploits tab to see the list.
References to Advisories, Solutions, and Tools
Here, you will find a curated list of external links that provide in-depth
information, practical solutions, and valuable tools related to
CVE-2026-24134.
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2026-24134 is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2026-24134
weaknesses.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Mirror of https://github.com/nomi-sec/PoC-in-GitHub
None
Python
📡 PoC auto collect from GitHub. ⚠️ Be careful Malware.
security cve exploit poc vulnerability
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2026-24134 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2026-24134 vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
Initial Analysis by [email protected]
Mar. 17, 2026
Action Type Old Value New Value Added CPE Configuration OR *cpe:2.3:a:studiocms:studiocms:*:*:*:*:*:*:*:* versions up to (excluding) 0.2.0 Added Reference Type GitHub, Inc.: https://github.com/withstudiocms/studiocms/commit/efc10bee20db090fdd75463622c30dda390c50ad Types: Patch Added Reference Type GitHub, Inc.: https://github.com/withstudiocms/studiocms/releases/tag/studiocms%400.2.0 Types: Release Notes Added Reference Type GitHub, Inc.: https://github.com/withstudiocms/studiocms/security/advisories/GHSA-8cw6-53m5-4932 Types: Exploit, Vendor Advisory -
New CVE Received by [email protected]
Jan. 28, 2026
Action Type Old Value New Value Added Description StudioCMS is a server-side-rendered, Astro native, headless content management system. Versions prior to 0.2.0 contain a Broken Object Level Authorization (BOLA) vulnerability in the Content Management feature that allows users with the "Visitor" role to access draft content created by Editor/Admin/Owner users. Version 0.2.0 patches the issue. Added CVSS V3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N Added CWE CWE-639 Added CWE CWE-862 Added Reference https://github.com/withstudiocms/studiocms/commit/efc10bee20db090fdd75463622c30dda390c50ad Added Reference https://github.com/withstudiocms/studiocms/releases/tag/studiocms%400.2.0 Added Reference https://github.com/withstudiocms/studiocms/security/advisories/GHSA-8cw6-53m5-4932